Changes

This PR does a further refactor of our internals. The main issue I was facing was the fact that I was trying to use the DevApp both in our internal dev server and the dev server spawned by external plugins such as Cloudflare.

This wasn't working and driving me nuts because DevApp uses a lot of Node.js APIs across the board. It was mental. So after thinking more about what @ascorbic said, we should try to use App instead, it actually made sense and it was the right approach. However, in dev, we handle a few things differently compared to production. For example, we handle 500 errors differently in dev.

So now, we have two apps:

• AstroServerApp (which uses its own AstroServerPipeline)
• DevApp (which uses its own DevPipeline)

AstroServerApp

It uses the code and business logic we currently use in our Astro server. The old DevPipeline has been renamed to AstroServerPipeline

DevApp

This new DevApp is mostly the same as App. They both use the same methods (such as render), they slightly differ in the match implementation, for example.

Since App and DevApp share the same logic, they are runtime-agnostic.

The new DevPipeline, for now, is a copy-paste of AppPipeline, however, we changed the logic of the function getComponentByRoute. In development, we don't have the compiled Astro files, so we need to dynamically import them e.g. import("path/to/file.astro). Eventually, in dev, our rollup plugin is triggered, and it should return the compiled code.

Testing

Minimal and react examples still work locally

Docs